Methods and systems for generating a horizon for use in an advanced driver assistance system (adas)

ABSTRACT

A method of generating a horizon for use by an ADAS of a vehicle involves using digital location-based data, driver data and/or vehicle data to determine the likelihood that different outgoing paths are taken at a decision point along a currently traversed road segment, and deriving a probability that each path may be taken. The probability may be based on one or more of: an angle of the path relative to the incoming path, the road class of the path, a speed profile of the path, historical paths taken by vehicles at the decision point, and historical paths taken at the decision point by the individual driver or vehicle.

FIELD OF THE INVENTION

The present invention relates to methods and systems for generating ahorizon for use in an Advanced Driver Assistance System (ADAS) of avehicle.

BACKGROUND TO THE INVENTION

Advanced Driver Assistance Systems are increasingly used in vehicles toprovide assistance to drivers in areas such as braking, collisionavoidance, and speed selection. Such systems may help to reduce driverworkload, and may be useful in improving safety, vehicle operatingefficiency, driver comfort and/or fuel efficiency.

Operation of an ADAS relies upon knowledge of the road ahead, and itsproperties. For example, the ADAS may take into account factors such asthe curvature or gradient of a section of the road ahead in order todetermine a suitable speed for traversing the section, and may then, forexample, control the braking subsystems of the vehicle in order toimplement the determined speed. Typically a subsystem of the ADAS, whichmay be known as an ADAS horizon provider subsystem, communicates withADAS applications of a vehicle network over a vehicle bus, such as aController Area Network (CAN) bus, in order to control vehiclesubsystems. Different ADAS applications may control different respectivevehicle subsystems in accordance with the information received from theADAS horizon provider over the vehicle bus. For example, there may beADAS applications in respect of braking, suspension, etc. The ADAShorizon provider subsystem provides ADAS horizon information which maybe used by the ADAS applications associated with given vehiclesubsystems to provide control of the respective vehicle subsystems usingthe ADAS horizon data.

One aspect of the operation of the ADAS horizon provider subsystemrelates to the generation of a suitable ADAS “horizon” for communicationover the vehicle bus to the vehicle subsystems. The ADAS horizoncomprises digital map information about a portion of the road networkahead, which is used by the ADAS applications to implement ADASfunctionality with respect to the vehicle subsystems. Determination ofthe ADAS horizon involves predicting the path or paths that the vehiclemay travel in the immediate future, to ensure that the necessary data istransmitted over the vehicle bus to allow implementation of ADASfunctions by the vehicle subsystems as the vehicle travels.

The ADAS horizon may include information about the course of a roadahead, and associated attributes of the road, such as curvature,gradient, etc which may be used by ADAS applications of the vehicle toimplement ADAS control of the vehicle subsystems. ADAS applicationsassociated with different vehicle systems may filter the provided ADAShorizon data to extract the information required for controlling theirrelevant subsystem. For example, road curvature data may be extractedfor use in controlling the braking system.

When determining a suitable portion of the road network ahead forinclusion in the ADAS horizon, it is necessary to balance providingsufficient data to ensure that ADAS functionality may be adequatelyimplemented by vehicle systems while avoiding overloading the vehicleADAS applications associated with the vehicle systems. The prediction ofthe path or paths that the vehicle may be expected to travel in the nearfuture is therefore fundamental to the generation of a suitable ADAShorizon. The determination of a suitable ADAS horizon may involvecertain challenges, for example depending upon whether the vehicle isfollowing a pre-calculated route or not, and to accommodate potentialdeviations of a vehicle from a pre-calculated route. For example, in asimple case, the ADAS horizon may comprise data relating only to theroad currently being traversed up to a predetermined distance from acurrent position. However, in such situations, the ADAS applications maybe left “blind” for a time if the driver deviates from the roadcurrently being traversed until a new ADAS horizon can be generated inrelation to the newly traversed road section.

The Applicant has realised that there is a need for improved methods andsystems for generating a horizon for use by an ADAS, and in particular,for predicting a path or paths that a vehicle may travel in theimmediate future when generating an ADAS horizon.

SUMMARY OF THE INVENTION

In accordance with a first aspect of the invention there is provided amethod of generating a horizon for use in an ADAS of a vehicle,comprising:

generating the horizon using one or more of: stored digitallocation-based data, vehicle data and driver data.

Thus, in accordance with the invention, generation of an ADAS horizoninvolves using stored digital location-based data and/or vehicle dataand/or driver data.

In accordance with a second aspect of the invention there is provided asystem for generating a horizon for use in an ADAS of a vehicle, thesystem comprising:

means for generating the horizon using one or more of; stored digitallocation-based data, vehicle data or driver data.

The present invention in this further aspect may include any or all ofthe features described in relation to the first aspect of the invention,and vice versa, to the extent that they are not mutually inconsistent.Thus, if not explicitly stated herein, the system of the presentinvention may comprise means for carrying out any of the steps of themethod described.

The means for carrying out any of the steps of the method may comprise aset of one or more processors configured, e.g. programmed, for doing so.A given step may be carried out using the same or a different set ofprocessors to any other step. Any given step may be carried out using acombination of sets of processors. The system may further comprise datastorage means, such as computer memory, for storing, for example, thedata indicative of the generated horizon, and/or the data used indetermining the horizon, i.e. the vehicle data, driver data and/ordigital location-based data. The means for generating the horizon may bea horizon generating subsystem of an ADAS system.

As used herein, the term “horizon” refers to a driving horizon for useby an ADAS of a vehicle. The horizon includes a prediction of one ormore paths that the vehicle may travel in the immediate future through aportion of a road network or data enabling such a prediction to be made.The road network comprises a plurality of road segments connected bynodes and is represented by digital map data indicative of each roadsegment and node, i.e. decision point. In preferred embodiments thehorizon comprises data indicative of the relative probability that eachof a plurality of paths may be taken by the vehicle at a decision point.The horizon may comprise digital map data indicative of the or eachpredicted path and/or data indicative of one or more attributes of theor each predicted path. This may allow data about an upcoming portion ofthe road network to be obtained in advance before the vehicle reachesthe relevant portion, to enable the ADAS to function. The portion of theroad network may be defined by a boundary of the horizon.

By using stored digital location-based data, vehicle data and/or driverdata to generate the ADAS horizon, it has been found that a usefulhorizon containing data necessary for appropriate guidance of thevehicle may be obtained. In particular, the use of such data has beenfound to allow the relative probability that each of a plurality ofpossible paths may be taken at a decision point to be more reliablydetermined. This may allow more accurate prediction of paths that may betaken by the vehicle to be made, resulting in more reliable operation ofan ADAS system of the vehicle based on the ADAS horizon, even where thevehicle diverges from an expected most probable path.

The generated horizon may extend from a current position of a vehicle toa predetermined distance ahead of the current position defining aboundary of the horizon. The ADAS horizon may extend to thepredetermined distance from the current vehicle position along the oreach predicted path. The distance may be up to 500 m, or up to 200 mand/or at least 100 m. A given distance ahead of a current positionrefers to a distance in the current direction of travel. The extent ofthe horizon may be chosen as desired for a given application. Thehorizon may extend to a given radius corresponding to the distance inthe direction of travel, e.g. through a 180 degree angle in the forwarddirection of travel.

As used herein, a “path” may comprise at least a portion of one or moreroad segments. A path is representative of a trajectory that may betaken by a vehicle through the road network. A path is a path defined byat least a portion of one or more road segments of a digital map. Thedigital map comprises a plurality of segments representative of roadsegments of a road network.

In accordance with the invention stored digital location-based data,vehicle data and/or driver data are used to generate the horizon.Preferably at least stored digital location-based data is used. One orboth of stored vehicle and driver data may additionally be used. Wherenot explicitly stated, and unless the context demands otherwise, it willbe appreciated that any combination of stored digital location-baseddata, vehicle data and/or driver data may be used.

The digital location-based data is, in preferred embodiments, digitalmap data.

In embodiments, the stored digital map data is representative of aplurality of road segments of a road network, the data representative ofeach road segment being associated with data indicative of one or moreroad segment attributes. The method may comprise using the attributedata associated with the road segment data to generate the horizon.

Attribute data associated with data representative of a road segment,and which may be used in generating the or each path, includes attributedata indicative of inherent properties of the road segment and/orindicative of vehicle flow along the segment. Vehicle flow attributedata may be historic vehicle flow data, and may comprise vehicle speedprofile data. The data may be time dependent i.e. in respect of a giventime period.

Attribute data of a road segment which may be used in generating thehorizon may include data indicative of one or more of: a geometry of theroad segment, a gradient of the road segment, an angle of the roadsegment, a road class of the segment, a speed limit associated with thesegment (whether recommended or legal), vehicle flow data indicative ofvehicle flow along the segment, and vehicle speed profile data.

Generation of the horizon may be based upon absolute values ofattributes associated with the or each road segment. However, in somepreferred embodiments the generation of the horizon is alternatively oradditionally based on a comparison of an attribute or attributes of aroad segment to the corresponding attribute or attributes of one or moreother road segments. Thus the relative values of an attribute orattributes may be considered. For example, the relative values ofattributes of any of the types discussed above, such as road class,gradient, angle, speed limit, speed profile etc. may be considered. Themethod may comprise comparing the data indicative of an attribute orattributes of one road segment with the corresponding attribute data ofanother road segment or segment in generating the horizon.

Digital location-based data that is used in embodiments of the inventionmay also relate to historical paths taken by vehicles e.g. based onvehicle “probe data” (as described in below detail below).

The vehicle or driver data is preferably stored vehicle or stored driverdata. The data preferably relates to the individual vehicle having theADAS for which the horizon is generated, and/or the individual driver ofthe vehicle. The vehicle data may comprise data indicative of one ormore parameters of the vehicle or driver. Vehicle data which may be usedin generating the horizon may include data indicative of one or more of:vehicle type, vehicle speed, historical movements of the vehicle, e.g. aturn history of the vehicle, frequency of travel of the vehicle along agiven segments of a road network, etc. The driver data may include dataindicative of the past behaviour of the driver, e.g. a turn history ofthe driver, etc.

The vehicle data may, in preferred embodiments, comprise data relatingto the historical movements of the vehicle.

The vehicle data may, in other embodiments, comprise data indicative ofa current movement of the vehicle, e.g. a speed, location or pathtravelled by the vehicle. Such data is preferably used in combinationwith digital location-based data in generating the horizon. Where thevehicle data is stored data the data preferably does not relate to thecurrent movement of the vehicle.

It will be appreciated that certain parameters of the vehicle may beindicative of parameters of a driver, e.g. relating to past behaviour ofthe driver or turn history. Such parameters may be considered to bedriver specific parameters of the vehicle. For example, an ADAS of avehicle may collect data relating to the specific behaviour of a driver.Where a vehicle may have multiple drivers, this may be based uponmovements of the vehicle where a particular driver has been identified.Thus, it will be appreciated that the vehicle parameters upon whichgeneration of the ADAS horizon may be based, may or may not be driverspecific parameters of the vehicle. In some cases driver specific datamight be identified through a driver profile and may be indicative ofthe behaviour of the driver when driving other vehicles. Thus driverdata may not necessarily be data relating to an individual vehicle.

In accordance with the invention, the step of generating the horizonusing the stored digital location-based data, vehicle data and/or driverdata, preferably comprises using the data to determine data indicativeof the relative probability that each of a plurality of possibleoutgoing paths associated with a decision point will be taken by thevehicle in the immediate future.

It will be appreciated that the methods described herein in relation toa given decision point may be carried out in respect of any additionaldecision points of the road network as desired.

As used herein, the “relative probability” of a path of a set of aplurality of possible outgoing paths at a decision point being taken bya vehicle in the immediate future refers to the probability that thevehicle may be expected to take the path relative to the probabilitythat the vehicle will take any of the other paths of the set of aplurality of possible outgoing paths at the decision point in theimmediate future. References to a probable path or any other referenceto probability or likelihood of a path should be understood to refer tothe probability of the vehicle travelling along the path in theimmediate future.

Preferably, for each respective possible outgoing path at the decisionpoint, data is determined indicative of a relative probability that thepath will be taken in preference to any other one of the possibleoutgoing paths. The method may comprise associating the relativeprobability data with data indicative of the path to which it relatesand/or the decision point to which it relates.

It will be appreciated that the definition of an “outgoing” path, andindeed the relative probability that a given path will be taken, willdepend upon the incoming path to the decision point. Accordingly therelative probability that each of the plurality of possible outgoingpaths is taken is by reference to a given incoming path.

The method may comprise the step of determining an incoming path to thedecision point with respect to which the outgoing paths are to bedefined. The incoming path is a path along which the vehicle is expectedto travel to reach the decision point. In preferred embodiments theincoming path is a continuation of a road segment along which thevehicle is currently travelling. Alternatively or additionally the pathmay be a portion of a known most probable path for the vehicle, such asa portion of a pre-calculated route. In these cases the portion of theknown path is preferably an end portion of the known path whichterminates at the decision point. However, these preferred embodimentsof the invention may still be applied to determining the relativeprobability that each of a plurality of other paths may be taken at adecision point even where an outgoing path at the decision pointcorresponding to a portion of a pre-calculated route is known.

The decision point may be any decision point defining a plurality ofpossible outgoing paths for which it is desired to determine a relativeprobability associated with taking each of the possible paths. Inembodiments the decision point is the next decision point to beencountered by the vehicle along a continuation of a currently traversedroad segment. It may be assumed that the vehicle will continue along thecurrently traversed road segment at least until the next decision pointis reached. Thus the path as far as the next decision point may beconsidered to be known.

In some embodiments the method comprises identifying a current locationof the vehicle, determining a road segment along which the vehicle iscurrently travelling, and identifying the next decision point to beencountered. The method may then comprise determining the relativeprobability that each of a plurality of outgoing paths associated withthe decision point will be taken in accordance with the methods of theinvention.

It is envisaged that the preferred methods of determining the relativeprobabilities associated with paths at a decision point may be carriedout “on the fly”. Thus, preferably the decision point is an upcomingdecision point or next decision point to be encountered. Nonetheless, itis envisaged that the method could be carried out with respect to anydecision point of a road network, or could be applied to determiningrelative probability values in advance that could be stored inassociation with data identifying each decision point to which theyrelate in a database or similar for subsequent use as desired. In thiscase, the incoming path with respect to which the outgoing path(s) aredefined may be arbitrarily chosen, and data may be obtained for a givendecision point in respect of multiple possible incoming paths.

In any of its embodiments, the method may comprise selecting a decisionpoint, and determining an incoming path and a plurality of outgoingpaths associated with the decision point for which relativeprobabilities are to be determined.

The decision point may be any type of decision point at which two ormore possible outgoing paths exist for a given incoming path. Thedecision point may be any form of intersection, roundabout, junction,crossing, divergence of a path, etc. The term “decision point” as usedherein also encompasses a plural junction where individual junctions areclose together. In these cases paths emanating from each junction may beconsidered to approximately emanate from a single decision point, andmay be treated as such.

The method preferably involves determining data indicative of a relativeprobability that each of a set of two or more possible outgoing pathswill be taken by the vehicle at the decision point (for a given incomingpath). Preferably the method comprises determining relative probabilitydata in respect of every possible outgoing path present at the decisionpoint in respect of the given incoming path. An outgoing path may bedefined as any path originating from the decision point other than theincoming path. The possible outgoing paths may or may not include allpotential outgoing paths associated with the decision point, and certainpaths may be excluded from consideration for various reasons e.g. asthey are considered to be in a direction close to that opposite to thedirection of travel, are below a significance threshold, etc. Forexample, the path corresponding to the incoming path but in the oppositetravel direction may not be considered for a junction, but may beconsidered for a roundabout. Such paths that are not considered are notdeemed to be “possible” outgoing paths. Unless the context demandsotherwise, references herein to an “outgoing path” should be understoodto refer to a “possible outgoing path”. The methods of the presentinvention are therefore carried out with respect to a set of a pluralityof possible outgoing paths at the decision point. The set of theplurality of possible outgoing paths are those paths for which relativeprobability data is desired to be determined, i.e. which paths areconsidered relevant paths for a given application.

In some embodiments in which one of the possible outgoing paths at thedecision point is known to correspond to a portion of a pre-calculatedroute, the method may comprise excluding that outgoing path from the setof plurality of outgoing paths whose relative probabilities aredetermined, or adjusting the calculations appropriately to ensure thatthis route is determined to be the most probable. This may be done byassigning the path corresponding to the route a probability of one and,for example, adjusting the probabilities of the other paths accordingly,or by adjusting the relative probabilities of the other paths such thatnone is higher than that of the path corresponding to the route.

The step of determining the data indicative of a relative probabilitythat each possible outgoing path of a plurality of paths may be taken bythe vehicle may comprise ranking each path according to the likelihoodthat the vehicle may be expected to travel along the path in preferenceto any other one of the paths of the set of a plurality of possibleoutgoing paths. Thus, the relative probability may be in terms of aqualitative ordering of the paths. In other embodiments the step maycomprise determining a probability factor in respect of each possibleoutgoing path indicative of the relative probability that the path willbe taken in preference to any other one of the paths. The probabilityfactor provides a quantitative measure of the relative probability thatthe path will be taken.

The step of determining the data indicative of the relative probabilitythat a given possible outgoing path may be taken may comprise using thestored digital location based data, vehicle data and/or driver data, aswill be described in more detail below. The step of determining therelative probability of a given possible outgoing path may furthercomprise using data indicative of the incoming path that the vehicle isexpected to travel to reach the decision point, attribute dataassociated with such a path and/or parameters of the vehicle as ittravels along the incoming path (e.g. speed, acceleration, etc).

The method may comprise storing the determined data indicative of therelative probability that each possible outgoing path will be taken. Thestored data may be indicative of a rank or probability factor for thepath. The method may comprise storing data indicative of a relativeprobability that the path will be taken in preference to any other oneof the paths for each possible outgoing path in association with dataidentifying the path. The method may further comprise storing dataindicative of the incoming path with respect to which the outgoing pathsare defined. The method may comprise storing the data indicative of therelative probability of a possible outgoing path being taken inassociation with data indicative of the decision point to which itrelates, e.g. the location of the decision point. The location of thedecision point may be in absolute terms or in relation to a distancealong an, for example, most probable path, etc.

Some preferred embodiments of the invention will now be describedillustrating the way in which different types of stored digitallocation-based, e.g. map data, vehicle data and/or driver data, may beused to determine the data indicative of the relative probability ofeach possible outgoing path being taken. It will be appreciated that anyof these embodiments may be combined as desired. For example,determination of the relative probability associated with each possibleoutgoing path may involve consideration of one or more of: the angleand/or road class of possible outgoing paths, past paths taken by adriver and/or vehicle, current vehicle speed, average speed associatedwith a path, and data indicative of the probability that paths wereselected historically based on “probe data”. A suitable probabilityfunction indicative of the relative probability of a path may beconstructed to take account of any or all of these factors, and with anappropriate weight assigned to each as desired.

The digital location-based data, e.g. digital map data, where used maybe data relating to a road segment defining the initial portion of therelevant outgoing path as it extends away from the decision point.

In some embodiments the step of determining the relative probabilitydata for each of the possible outgoing paths may comprise using storeddigital map data. In these embodiments the step of determining therelative probability that different possible outgoing paths will betaken may comprise using attribute data associated with road segmentsdefining at least the initial portion of the outgoing paths at adecision point. The attribute data may be of the any of the typesdiscussed above. The attribute data may be used directly or may be usedto determine other data based thereon which is used in thedetermination.

In certain embodiments the method comprises determining the dataindicative of a relative probability that each of the possible outgoingpaths will be taken at the decision point using data indicative of oneor both of an angle defined between the outgoing path and the incomingpath and road class of the outgoing path.

The angle data may be determined using stored digital map data. Forexample, the angle data may be determined using attribute dataassociated with data indicative of the road segment defining (at leastthe initial portion of) the possible outgoing path and optionally alsothe incoming path, or data derived therefrom. The angle data may bedetermined indirectly using data indicative of the trajectory of eachroad segment or data relating to the angle of the segment defining theoutgoing path with respect to the decision point, etc The road class isindicative of the relative importance of the road, and may be afunctional road class. According to standard definitions, a road may beclassified such that a higher road class is indicative of a relativelyless significant road. In other words, a highway or motorway has a lowerfunctional road class than a minor road.

In embodiments the method comprises determining that a possible outgoingpath is relatively more probable, i.e. there is a relatively higherlikelihood that the vehicle will take the path in preference to eachother possible outgoing path, when the outgoing path is associated witha relatively lower angle relative to the incoming path and/or whenassociated with a road class indicative of relatively greatersignificance.

The determination may be based on any function of the angle and/or roadclass. Where the determination is based on a function of both angle androad class, the function may be adapted as appropriate to weight thecontribution of angle or road class to the determination as desired.

In embodiments the method comprises determining the data indicative of arelative probability that each of the possible outgoing paths will betaken at the decision point using data indicative of whether a manoeuvreat a decision point is deemed a “priority manoeuvre” in the digital mapdata. For example, a complicated manoeuvre at a junction may also be acommon manoeuvre, and is marked as a special case in the digital mapdata for the junction. A manoeuvre from an incoming path to an outgoingpath denoted as a priority manoeuvre in the digital map data may be, andpreferably is, deemed relatively more probable than it would otherwisebased on, for example, the angle defined between the outgoing path andthe incoming path and road class of the outgoing path.

Similarly, embodiments of the method may, additionally or alternatively,comprise determining the data indicative of a relative probability thateach of the possible outgoing paths will be taken at the decision pointusing data indicative of whether a manoeuvre at a decision point isdeemed a “discouraged manoeuvre” or an “illegal manoeuvre” in thedigital map data. For example, a sequence of manoeuvres at a pluralityof sequential decision points, e.g. junctions, may be marked as anillegal manoeuvre in the digital map data, and can be assigned a zero,or close to zero, probability when generating the horizon. A“discouraged manoeuvre” is the converse of the “priority manoeuvre”mentioned above, and refers to an manoeuvre that appears favourable,e.g. based on the angle defined between the outgoing path and theincoming path and road class of the outgoing path, but is in realitydangerous or not commonly used. A manoeuvre from an incoming path to anoutgoing path denoted as a discouraged manoeuvre in the digital map datamay be, and preferably is, deemed relatively less probable than it wouldotherwise based on, for example, the angle defined between the outgoingpath and the incoming path and road class of the outgoing path.

Alternatively or additionally, the data indicative of the relativeprobability that each of the possible outgoing paths will be taken isdetermined based on data indicative of historical paths taken by theindividual driver and/or vehicle at the decision point. The data isspecific to the given decision point. The data is specific to anindividual driver and/or vehicle. Knowledge of past behaviour of thedriver or travel of a vehicle may enable predictions about futurebehaviour/travel, and hence future paths, to be more accurately made.

In this regard, it is envisaged that as a driver may use multiplevehicles, the historical path data may be obtained by reference to anindividual driver profile, and may be assumed to be applicable wheneverthe driver is driving a vehicle. In other embodiments, the data may bespecific to a vehicle regardless of who the driver may be. In manycases, where a vehicle is always driven by the same driver, there willbe no difference between the historical travel of the vehicle or driver.These embodiments may be used in addition to consideration of factorsbased on stored digital map data, such as the angle and/or class ofpaths.

The historical path data is indicative of a historic probability of eachof the plurality of possible outgoing paths being taken by the driverand/or vehicle at the decision point with respect to the incoming path.The data may be historic probability data or data allowing historicprobability data to be determined. The data may, for example, comprisedata indicative of a frequency that each of the paths was taken. Forexample, it may be determined from frequency data that thedriver/vehicle has taken outgoing path 1 at a given decision point 70%of the time previously when approaching along incoming path 2. Themethod may comprise selecting data relating to each incoming-outgoingpath combination to be considered from historical data relating to pathstaken by the vehicle and/or driver at the decision point. Thus, thehistorical path data may include data relating to otherincoming-outgoing path combinations for the decision point.

The method may comprise associating a relative probability that a givenoutgoing path will be taken in dependence upon a historic relativeprobability of the path having been taken by the driver and/or vehicle.A relatively higher probability may be associated with a path having arelatively higher probability of having been taken historically by theindividual driver and/or vehicle.

Data relating to historical paths travelled by the vehicle and/or drivermay be obtained, for example, from the ADAS of the vehicle or anavigation device associated therewith.

In some embodiments the method further comprises obtaining the dataindicative of the historic paths taken by the driver and/or vehicle atthe decision point. In some embodiments the method comprises determiningsuch data from a database indicative of historic paths taken by thedriver and/or vehicle at each of a plurality of decision points in theroad network. The database may comprise data indicative of the historicpaths taken in association with data indicative of the location of theor each decision point.

The method extends to the step of generating and/or providing such adatabase. In embodiments the method comprises obtaining and storing dataindicative of a frequency with which each of a plurality of differentpossible outgoing paths at one or more, and preferably a plurality of,decision points of a road network have been taken by an individualdriver and/or vehicle with respect of at least one possible incomingpath, and preferably with respect to a plurality of, or each possibleincoming path for the or each decision point. For example, each pathassociated with a given decision point may be assigned an identifier,and a matrix constructed identifying a frequency with which the driveror vehicle has travelled across the decision point for each of aplurality of possible incoming paths to each of a plurality of possibleoutgoing paths.

The present invention thus extends to a data product comprising such adatabase.

While in some embodiments the or each determined path is determinedbased on data indicative of historic paths taken by an individual driveror vehicle, in other embodiments, or in addition, data indicative ofhistorical paths taken by multiple vehicles may be used in determiningthe or each path (as is described in more detail below).

Alternatively or additionally, the method comprises determining the dataindicative of a relative probability that each of the plurality ofpossible outgoing paths will be taken using speed profile dataassociated with road segments defining the respective paths. The speedprofile is a speed profile based on data indicative of the historicalspeed of vehicles travelling along the road segment defining the atleast the portion of the path extending from the decision point. Speedprofile data may be an attribute associated with each road segment ofthe road network, and therefore may form part of the stored digital mapdata.

The digital map data representing a road segment defining a given pathmay be associated with data representative of a speed profile for thesegment. The speed profile is preferably indicative of an average speedassociated with the segment, and preferably the method comprises usingaverage speed data indicated by the speed profile data associated with aroad segment defining each possible outgoing path in determining therelative probability data. The speed profile may be associated with thesegment as a whole, or data indicative of one or more speed profiles inrespect of one or more positions along the segment may be associatedwith the segment. Thus, in these embodiments each of the outgoing pathsthat is considered may be represented by a road segment having speedprofile data associated therewith. The speed profile data used in theseembodiments may be time dependent. In embodiments speed profile dataindicative of a speed profile for each of a plurality of different timeperiods may be associated with a given road segment. The method mayfurther comprise selecting speed profile data from speed profile dataassociated with a given segment defining an outgoing or incoming paththat relates to a period including the current time or an expected timeat which the segment is to be traversed.

The method may comprise comparing speed data, e.g. average speed data,indicated by the speed profile data associated with the segmentsrepresenting different ones of the possible outgoing paths to determinethe data indicative of the relative probability that the path will betaken.

In some embodiments a relatively higher probability is associated with apath having a speed profile indicative of a relatively higher averagespeed associated therewith. A higher average speed according to thespeed profile data may be indicative of a more significant road. Thusconsideration of speed profile data may be used as an indirect way ofassessing road class.

Alternatively or additionally, in other embodiments the method maycomprise determining the relative probability that each of the pluralityof possible outgoing paths will be taken by comparing speed profile dataassociated with the road segments representing each given path with acurrent speed of travel of the vehicle along the incoming path.Preferably the method comprises comparing a current speed of the vehiclealong the incoming path to that of each possible outgoing path. In theseembodiments a relatively higher probability may be associated with apossible outgoing path where a relatively smaller difference existsbetween an incoming current speed of the vehicle and the average speedassociated with the outgoing path based on the speed profile dataassociated with the outgoing path. Thus, it may be assumed that anoutgoing path is more probable if it has an average speed closer to thatof the incoming path that is being travelled.

The speed profile data associated with a given segment may be used as aweighting factor together with the other factors described herein, oralone, to determine the overall probability that a path corresponding tothe segment will be taken.

In preferred embodiments the speed profile data is based on datarelating to the position of a plurality of devices associated withvehicles with respect to time. Such data may be referred to as vehicle“probe data”, and any references to vehicle “probe data” herein, shouldbe understood to refer to such positional data. As the devices areassociated with respective vehicles, the position of the devices may beconsidered to correspond to the position of the vehicles. The method mayextend to the steps of obtaining such positional data and/or using thedata to determine the speed profile data and associating the data withrespective road segment(s) to which it relates. The vehicle positionaldata may be of any of the forms described below in relation to thefurther embodiments in which the relative probability data is determinedusing historical probe data.

The speed profile data associated with a road segment is thus, at leastin preferred embodiments, indicative of an average speed of travel fortraversing the road segment during one or more, and preferably aplurality of, time periods. For example, the sped profile data can showhow the average speed changes across a day, e.g. on a hourly basis. Therelative probability that each outgoing path from the decision pointwill be taken is preferably determined using the average speed for thetime period appropriate for the time at which the horizon is generated.For example, the time period matching the current time may be chosen orthe time period matching the time at which the vehicle will reach thedecision point (which will typically be the same as the horizon isintended to be a reflection of paths that may be travelled in theimmediate future).

The invention is not limited to the use of speed profile data based on“probe data” in determining the probabilities of paths. For example, themethod may comprise using data relating to the position of devicesassociated with vehicles with respect to time, i.e. vehicle probe data,and which is preferably obtained over a long period of time, e.g. weeks,months, etc (i.e. can be referred to as “historical data”), indetermining the relative probabilities associated with taking eachpossible outgoing path at a decision point, or more generally topredicting one or more possible paths in the horizon.

The method may comprise determining the relative probability data usingdata indicative of a historic relative probability that each of theplurality of possible outgoing paths from the decision point has beentaken in respect of the incoming path based on the aforementionedhistorical probe data. The method may comprise associating a relativelyhigher probability with a possible outgoing path that is associated witha relatively higher probability of having been selected based on thehistorical probe data. The relative probability that the paths werechosen historically may be used alone, or as a weighting factor togetherwith other factors to determine the relative probability that paths willbe chosen.

The method may extend to determining the data indicative of the historicrelative probability that each of the plurality of possible outgoingpaths has been taken for the given incoming path. This may be carriedout using historical data relating to the position of a plurality ofdevices associated with vehicles with respect to time in a portion of aroad network comprising the decision point. The method may compriseusing the positional data to determine a relative frequency with whichvehicles have taken each of the plurality of possible outgoing pathsfrom the decision point in respect of the incoming path. The historicalprobability data may be obtained using a count indicative of the numberof times that each path is taken. In other embodiments the method maycomprise obtaining the historic relative probability data from adatabase comprising data indicative of the frequency with which each ofa plurality of possible outgoing paths has been taken at one or more,and preferably a plurality of, decision points of a road network for oneor more, and preferably a plurality of, possible incoming paths of theor each decision point.

The historical probability may be time dependent. Thus, multiplehistorical probabilities may be determined for a given path in respectof different time periods. For example, a count indicative of the numberof times that a given path is taken by a device associated with avehicle in a given time frame may be determined and used in determiningthe historic probability for a path. The step of determining theprobability that a given path will be selected using the historicalpositional data may comprise using historic probability data relating todevices associated with vehicles approaching the decision point in atime period corresponding to a current time or an expected time ofarrival at the decision point.

The method may extend to obtaining the positional data. The step ofobtaining the positional data may comprise receiving the data fromdevices associated vehicles, or may comprise accessing stored positionaldata. The method may thus comprise obtaining positional data relating tothe movement of a plurality of devices associated with vehicles withrespect to time in a road network, and filtering the data to obtain datarelating to the travel of devices (and hence vehicles) along the or eachof the plurality of possible outgoing paths from the decision point inrespect of the given incoming path. The method may then comprise usingthe data to obtain a count of the number of times each possible outgoingpath is taken, and determining a relative probability that each outgoingpath was taken for the given incoming path.

In some embodiments the method comprises generating and/or providing aprobability matrix, the probability matrix comprising, in respect ofeach of one or more decision points of a road network, data indicativeof the relative probability that each of a plurality of possibleoutgoing paths at the decision point will be taken by a vehicle for eachof one or more possible incoming paths, wherein the data indicative ofthe relative probability that a given possible outgoing path will betaken is based upon historical data relating to the position of multipledevices associated with vehicles with respect to time. Preferably thematrix comprises data indicative of the relative probability of eachpossible outgoing path being taken at one or more, and preferably aplurality of, decision points for each possible incoming path at thedecision point. The method may comprise using such a probability matrixin determining the relative probability data for the different outgoingpaths. The data of the probability matrix may be time dependent, andthus may be based on data relating to movements of devices associatedwith vehicles in a given time period.

The method may comprise storing such a probability matrix.

The present invention extends to a data product comprising such aprobability matrix.

In accordance with a further aspect of the invention there is provided adata product comprising a probability matrix having, in respect of eachof one or more decision points of a road network, data indicative of therelative probability that each of a plurality of possible outgoing pathsat the decision point will be taken by a vehicle for each of one or morepossible incoming paths, wherein the data indicative of the relativeprobability that a given possible outgoing path will be taken is basedupon positional data relating to the movements of a plurality of devicesassociated with vehicles with respect to time.

The present invention in this further aspect may include any or all ofthe features described with reference to the other aspects of theinvention to the extent they are not mutually exclusive.

In accordance with the invention in any of its aspects or embodimentsinvolving a probability matrix, the step of providing the probabilitymatrix may comprise obtaining positional data relating to the positionof multiple devices associated with vehicles with respect to time in aroad network, and filtering the positional data to obtain dataindicative of the travel of vehicles along each possible outgoing pathat the or each decision point of the road network, and with respect tothe or each incoming path at the or each decision point. The filtereddata may then be used to determine the relative probability that each ofthe plurality of paths at a decision point is taken.

In accordance with any embodiment using positional data, the method mayextend to the step of obtaining the positional data relating to themovement of devices associated with vehicles. The step of obtaining thepositional data may or may not comprise receiving the data from the oneor more devices. In some arrangements the step of obtaining the data maycomprise accessing the data, i.e. the data being previously received andstored. In arrangements in which the step of receiving the data involvesreceiving the data from the devices, it is envisaged that the method mayfurther comprise storing the received positional data before proceedingto carry out the other steps of the present invention, and optionallyfiltering the data. The step of receiving the positional data need nottake place at the same time or place as the other step or steps of themethod.

In embodiments the positional data is received at a central controller,such as a server system. The server may carry out the steps of using thepositional data to determine a relative probability that each of aplurality of paths will be taken, or to determine the probabilitymatrix.

The positional data used in accordance with the invention, at least inpreferred embodiments, is collected from one or more, and preferablymultiple devices, and relates to the movement of the devices withrespect to time. Thus, the devices are mobile devices. It will beappreciated that at least some of the positional data is associated withtemporal data, e.g. a timestamp. For the purposes of the presentinvention, however, it is not necessary that all positional data isassociated with temporal data, provided that it may be used to providethe information relating to the traffic control signal in accordancewith the present invention. However, in preferred embodiments allpositional data is associated with temporal data, e.g. a timestamp.

The devices are associated with vehicles. The position of a device canbe assumed to correspond to the position of a vehicle. Thus referencesto positional data obtained from devices associated with vehicles, maybe replaced by a reference to positional data obtained from a vehicle,and references to the movement of a device or devices may be replaced bya reference to the movement of a vehicle, and vice versa, if notexplicitly mentioned. The device may be integrated with the vehicle,e.g. in-built sensor or navigation apparatus, or may be a separatedevice associated with the vehicle, such as a portable navigationapparatus. Of course, the positional data may be obtained from acombination of different devices, or a single type of device, e.g.devices associated with vehicles.

The devices may be any mobile devices that are capable of providing thepositional data and sufficient associated timing data for the purposesof the present invention. The device may be any device having positiondetermining capability. For example, the device may comprise means foraccessing and receiving information from WiFi access points or cellularcommunication networks, such as a GSM device, and using this informationto determine its location. In preferred embodiments, however, the devicecomprises a global navigation satellite systems (GNSS) receiver, such asa GPS receiver, for receiving satellite signals indication the positionof the receiver at a particular point in time, and which preferablyreceives updated position information at regular intervals. Such devicesmay include navigation devices, mobile telecommunications devices withpositioning capability, position sensors, etc.

The steps of the methods described herein in any of its embodiments forgenerating a horizon are preferably carried out by a horizon generatingsubsystem of an ADAS. The ADAS is associated with a vehicle. The horizongenerating subsystem may be provided by a suitable software module ormodules, for example. The horizon generating subsystem is preferably incommunication with one or more ADAS applications of a vehicle over avehicle communication network, e.g. CAN bus.

The method may further comprise the step of storing the digital locationbased data, the vehicle data and/or driver data used in generating thehorizon.

Digital location based data and/or data indicative of vehicle or driverparameters may be stored in any location provided that it is accessiblefor use in generating the horizon, e.g. to a subsystem for generatingthe horizon. A horizon generating subsystem may comprise means forstoring the digital map data and/or vehicle or driver parameters used ingenerating the horizon, or such data may be stored separately to thehorizon generating subsystem. Similarly horizon data, e.g. probabilitydata, may be stored by a memory of the horizon generating subsystem orelsewhere.

Preferably the digital location based data, vehicle data and/or driverdata, or, where determined, probability data is stored locally to thevehicle, e.g. on a memory of the ADAS.

The method may further comprise the step of using the determined horizondata, e.g. relative probability data for a plurality of outgoing pathsassociated with a decision point, to determine one or more predictedpaths along which the vehicle can be expected to travel in the immediatefuture, e.g. one or both of a most probable path and at least onealternative path. The at least one alternative path preferably comprisesat least a most probable alternative path. The method may comprisestoring data indicative of the or each determined path. The one or moreof the most probable outgoing path and the at least one alternative pathare preferably outgoing paths at the decision point.

The step of generating the horizon may comprise determining a mostprobable path the vehicle may be expected to travel in the immediatefuture, and at least one alternative path, wherein the stored digitallocation-based data, vehicle data and/or driver data is used indetermining the most probable path and/or the at least one alternativepath.

In preferred embodiments in which relative probability data isdetermined for following each of a plurality of different possibleoutgoing paths at a decision point, the method may comprise determininga most probable outgoing path based on the probability data to betravelled by the vehicle from the decision point and/or determining therelative probabilities associated with one or more, and preferably aplurality of, alternative outgoing paths at the decision point using theprobability data.

The methods and systems of the present invention are applicable whetheror not the vehicle is following a pre-calculated route. In someembodiments the vehicle is a vehicle that is following a pre-calculatedroute, while in other embodiments the vehicle is a vehicle that is notfollowing a pre-calculated route. In the latter case, the vehicle willbe so-called “free driving”.

The most probable outgoing path based on the relative probability datamay be taken to be the most probable path to be travelled by the vehiclein embodiments in which the vehicle is not following a pre-calculatedroute.

As used herein, a “pre-calculated route” refers to a route that has beencalculated between an origin and a destination. The route may be a routethat has been pre-calculated by a navigation device associated with thevehicle. The navigation device may be an integrated or portablenavigation device. The pre-calculated route is, in these embodiments, aroute that has been calculated before the step of generating the ADAShorizon takes place. The method may further comprise the step ofcalculating a route that is to be followed by the vehicle between anorigin and a destination prior to the step of generating the ADAShorizon, and the system may comprise means for calculating a route. Theroute may be pre-calculated before the vehicle commences travel, or maybe a route that is calculated en-route, e.g. in the event of a deviationfrom an originally planned route. The method may comprise generating theADAS horizon during travel of the vehicle along the pre-calculatedroute.

When the vehicle is following a pre-calculated route, the most probablepath may be assumed to correspond to a portion of the pre-calculatedroute ahead. Thus, in embodiments in which the vehicle is following apre-calculated route, the most probable path, and hence in embodimentsthe most probable outgoing path at the decision point, is assumed tocorrespond to the pre-calculated route, or the outgoing pathcorresponding to a portion thereof. This may or may not be the same asthe most probable path indicated in preferred embodiments by therelative probabilities determined using the stored digitallocation-based data, vehicle data and/or driver data. In someembodiments in which one of the possible outgoing paths is known tocorrespond to a portion of a pre-calculated route, the method maycomprise excluding that outgoing path from the set of plurality ofoutgoing paths whose relative probabilities are determined, or adjustingthe calculations appropriately to ensure that this route is determinedto be the most probable, as described above.

Where an outgoing path corresponds to a pre-calculated route, the methodof the present invention in its preferred embodiments may be used todetermine the relative probabilities that each of a plurality ofoutgoing paths other than that corresponding to the pre-calculated routewill be taken at the decision point. These paths will providealternative paths diverging from the pre-calculated route at thedecision point. The present invention may then provide the ability todetermine the relative probability that the vehicle will follow any ofthese alternative paths if the path of the vehicle diverges from themost probable path, i.e. that corresponding to the pre-calculated routeat the decision point.

Determining of an alternative path emanating from a decision point aswell as the most probable path is advantageous as the alternative pathmay be taken to be the most likely path to be taken if the vehiclediverges from the most probable (main) path. By including dataindicative of the probability that different alternative paths may betaken at the decision point in the horizon, the ADAS may be able tocontinue to operate, and obtain data relating to the path, if thevehicle deviates from the expected main path, reducing the likelihood of“blind driving”.

The method preferably comprises providing storing data indicative of thegenerated horizon and/or providing data indicative of the generatedhorizon over a vehicle bus to one or more ADAS applications of thevehicle (e.g. to the client side of the vehicle ADAS). Preferably thesesteps are carried out by a horizon generating subsystem of the ADAS.

The ADAS applications are for controlling respective subsystems of thevehicle. The one or more ADAS applications may be arranged forcontrolling one or more of: a braking function, the suspension, and thespeed selection subsystem of the vehicle.

In embodiments in which the step of generating the horizon comprisesdetermining one or more predicted paths, e.g. one or both of a mostprobable path and an alternative path, the method may comprise storingdata indicative of the or each path and/or providing, e.g. transmittingsuch data over a vehicle bus to one or more ADAS applications of thevehicle for use by the one or more applications.

In embodiments in which data indicative of one or more predicted path isstored and/or provided over the bus, the data may comprise one or moreattributes of the path, or data allowing such attributes to bedetermined. The attribute data may comprise, as needed, informationidentifying a location associated with the one or more attributes. Forexample, the attribute data may indicate the start and end of a portionof a road segment with high curvature.

Attribute data in respect of a path of a horizon refers to properties ofthe predicted path ahead of a vehicle's current position, and mayinclude any or all of: a gradient of a segment, a curvature of asegment, a height of a segment, geometry of a segments, and a speedprofile associated with the segment. Thus the attribute data may reflectinherent properties of the segment, or for example relate to expectedvehicle speed data along the segment. The attribute data may be anyattribute data that may be used by one or more ADAS application toimplement one or more ADAS function. Thus, in some embodiments, themethod may further comprise an ADAS application of the vehicle using theattribute data transmitted over the vehicle bus to carry out one or moreof: issuing a speed warning, providing a speed recommendation, andautomatically controlling the braking function of the vehicle.

Preferably such attribute data is provided at least in respect of adetermined most probable path, and in some instances only for the mostprobably path. In these latter embodiments preferably data indicatingthe presence and/or location of one or more alternative paths along themost probably path is provided over the bus. The data indicative of thepresence of the one or more alternative paths preferably comprises dataindicative of the relative probability that the path will be taken atthe decision point determined in accordance with the invention. Inpreferred embodiments relative probability data is provided for eachalternative path for which relative probability data has beendetermined. In these embodiments, the ADAS applications would use theindication of the presence of an alternative path to request furtherdata, e.g. attribute data, from the horizon generator when the vehicleis found to diverge from a most probable route.

It will be appreciated that the methods in accordance with the presentinvention may be implemented at least partially using software. It willthis be seen that, when viewed from further aspects, the presentinvention extends to a computer program product comprising computerreadable instructions adapted to carry out any or all of the methoddescribed herein when executed on suitable data processing means. Theinvention also extends to a computer software carrier comprising suchsoftware. Such a software carrier could be a physical (ornon-transitory) storage medium or could be a signal such as anelectronic signal over wires, an optical signal or a radio signal suchas to a satellite or the like.

The present invention in accordance with any of its further aspects orembodiments may include any of the features described in reference toother aspects or embodiments of the invention to the extent it is notmutually inconsistent therewith.

It should be noted that the phrase ‘associated therewith’ in relation toone or more segments should not be interpreted to require any particularrestriction on data storage locations. The phrase only requires that thefeatures are identifiably related to a segment. Therefore associationmay for example be achieved by means of a reference to a side file,potentially located in a remote server.

Advantages of these embodiments are set out hereafter, and furtherdetails and features of each of these embodiments are defined in theaccompanying dependent claims and elsewhere in the following detaileddescription.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the present invention will now be described, byway of example only, and with reference to the accompanying drawings inwhich:

FIG. 1 shows the components of an exemplary ADAS system associated witha vehicle, which may be used to implement the methods of the presentinvention;

FIG. 2 schematically illustrates the concept of an ADAS horizon;

FIG. 3A illustrates the result of applying a method for determining therelative probability of outgoing paths in accordance with the inventionto a junction with four outgoing paths, where no route has beencalculated;

FIG. 3B shows the corresponding results where there is a pre-calculatedroute;

FIG. 4A illustrates the way in which the methods of the presentinvention may be applied to determining probabilities of paths at aroundabout;

FIG. 4B illustrates a way in which the methods of the present inventionmay be applied to a plural junction;

FIG. 5A illustrates a portion of a road network ahead of a currentposition of a vehicle up to a distance in the direction of traveldefined by a limit of the distance that the ADAS horizon will extendonce generated;

FIG. 5B illustrates a number of paths which may be taken through thenetwork;

FIG. 5C illustrates the way in which these paths may be represented toan ADAS application;

FIGS. 6A, 6B and 6C illustrate different ways in which information aboutpredicted paths in the road network may be represented to the ADASapplications.

DETAILED DESCRIPTION OF THE FIGURES

FIG. 1 is a schematic illustration of the components of an exemplaryADAS system associated with a vehicle, which may be used to implementthe methods of the present invention.

The ADAS system 1 includes a horizon generating subsystem 3, whichcommunicates horizon data over a Controller Area Network (CAN) bus 5 toa plurality of ADAS applications 7, 9 and 11. The ADAS applications arearranged to implement ADAS functionality in controlling respectivesubsystems of the vehicle. For example, the ADAS applications may be forcontrolling braking, speed selection and suspension vehicle subsystemsrespectively. In use, the respective ADAS applications filter therelevant data from the horizon data for use in controlling theirassociated vehicle subsystem.

The horizon providing subsystem 3 is arranged to generate dataindicative of a driving horizon which is used by the ADAS applications(the “ADAS horizon”). The ADAS horizon is an electronic horizoncomprising data indicative of one or more predicted paths ahead of acurrent position of a vehicle that it may be expected the vehicle willtravel along. The ADAS horizon is based on digital map data.

In order to provide ADAS functions, the ADAS applications requireinformation about the road ahead, and its attributes, e.g. gradient,curvature, speed limit, etc. The ADAS horizon provides this informationin respect of the one or more predicted paths up to a given distanceahead of the current position. The distance ahead may be 200 m. The ADAShorizon data that is transmitted over the vehicle bus 5 to the ADASapplications contains at least attribute data of the most probable path(up to a certain, often predetermined, extent ahead of the vehicle). TheADAS horizon generating subsystem 3 provides the attribute data inrelation to any attributes that may be required by the different ADASapplications 7, 9, 11, or data allowing such attribute data to berequested by the applications, and the respective subsystems may thenselect or request the attribute data relevant to their operation. Forexample, data relating to the curvature of the path ahead may beselected by an ADAS application for controlling braking of the vehicle.The attribute data may be provided in fields to facilitate filtering ofrelevant data by the ADAS applications.

The horizon generating subsystem 3 is arranged to determine a horizon inaccordance with any of the embodiments described herein, and to causethe horizon data to be transmitted over the vehicle bus to the ADASapplications. The horizon generating subsystem 3 may be arranged to bein communication with a memory for storing generated horizon data. Itwill be appreciated that as described below, not all horizon datadetermined is necessarily transmitted at a given time over the vehiclebus. For example, data relating to alternative paths rather than adetermined most probable path may be determined and stored, but nottransmitted over the bus unless required to avoid overloading the ADASapplications. The ADAS horizon generating subsystem is also incommunication with digital map data. This is used in determining thehorizon. In some arrangements the ADAS horizon generating subsystem maybe implemented using a software module separate from a digital map datastore, or may otherwise include means storing such data. Thus thedigital map data providing and horizon generating functions may beimplemented separately or as part of a combined system.

FIG. 2 schematically illustrates the concept of an ADAS horizon. It maybe seen that the electronic ADAS horizon 10 provides the ADAS withinformation about the path ahead in a similar manner to a vehicle sensorhorizon 12, but may provide information about the path beyond the limitof a vehicle sensor horizon, e.g. around a corner, and regardless ofweather conditions, as the ADAS horizon is based upon digital map data.

At various points in a road network there will be nodes, i.e. decisionpoints at which the vehicle may have a choice of possible outgoingpaths. The present invention relates, in embodiments at least, to amethod of more reliably determining the most probable path at a decisionpoint, and the relative probability that each of a plurality ofalternative paths may be taken. Some exemplary methods will be describedby reference to a decision point that is a junction.

At a given time, a vehicle has a current position defined on aparticular road segment. It may be assumed that the continuation of thesegment forms the most probable path until the first junction isreached. At the first junction the method of the present invention maybe used to determine the relative probability that each of the possibleoutgoing paths may be taken. This enables a determination to be made asto which of the plurality of outgoing paths forms the continuation ofthe main path, if this is not already known (e.g. from a pre-calculatedroute), and which form alternative paths. A determination is also madeas to the relative likelihood that one of these alternative paths may betaken.

In order to determine this, a probability is determined for eachoutgoing path at a decision point indicative of the likelihood that thepath will be chosen in preference of all other possible outgoing paths.In this process, certain outgoing paths which are considered not to bepossible outgoing paths may be excluded from the determination, e.g.they may be designated “restricted” paths. These may be excluded byassigning each a probability of “0”.

The way in which the probability for each outgoing path is determined isdependent upon whether the vehicle is following a pre-calculated route.

Where no route has been pre-calculated, a probability is determined foreach outgoing path at a decision point indicative of the likelihood thatthe path will be taken to the detriment of all other outgoing paths.This is done using an algorithm operating in one of the mannersdescribed below. The most probable path may be determined as the mostprobable path continuing from the decision point. Each other outgoingpath may then be classified as an alternative path.

Data is stored indicative of the identity and probability associatedwith the determined most probable path and each alternative path. Thisdata is associated with data indicative of the junction to which itrelates.

When a route is pre-calculated, it may be assumed that the most probableoutgoing path at the decision point is the outgoing path from thejunction which is along the pre-calculated route. This may override anyrestriction of the path. The remaining non-restricted outgoing paths aredetermined to be alternative paths.

Probabilities are determined for each of the other paths as describedfor the embodiment with no pre-calculated route, but each probability isdivided by two to avoid the path being more probable than the pathcorresponding to the pre-calculated route, but maintaining the rankingof the other paths. The probability of the path corresponding to thepre-calculated route is taken to be 100% minus the sum of theprobabilities of the other outgoing paths.

Data is stored indicative of the identity and probability of eachalternative path associated with data indicative of the junction towhich this relates.

The probability that a given possible outgoing path from the junctionwill be taken may be calculated using a suitable algorithm. Someembodiments according to which an algorithm may operate will now bedescribed.

In one embodiment the probability is a factor of the angle a an outgoingpath makes with the line of the path along which the vehicle is expectedto enter the junction, i.e. the expected incoming path, and the roadclass c of the outgoing path.

For an intersection with n outgoing paths, we will have n probabilities,between which we can have the following relation:

P ₁α₁ =P ₂α₂ = . . . =P _(i)α_(i) = . . . =P _(n)α_(n)

where α is a coefficient for an outgoing path, and is defined by:

$a_{i} = {a_{i} + \frac{k}{N_{c} - c_{i}}}$

where:a_(i) is the angle between the ith outgoing path and the incoming path;c_(i) is the road class of the ith outgoing path;N_(c) is the total number of road classes; andk is a coefficient, typically determined empirally.

Given the first relation, we can use one of the probabilities to expressall the others:

$P_{j} = {\frac{\alpha_{i}}{\alpha_{j}}P_{i}}$

And we know that the sum of all the probabilities is 1, thus:

P ₁ +P ₂ + . . . +P _(i) + . . . +P _(n)=1

From the last two relations we obtain:

${\alpha_{i}{P_{i}( {\frac{1}{\alpha_{1}} + \frac{1}{\alpha_{2}} + \ldots + \frac{1}{\alpha_{i}} + \ldots + \frac{1}{\alpha_{n}}} )}} = 1$

And therefore each probability can be calculated as:

$P_{i} = \frac{1}{\alpha_{i}( {\frac{1}{\alpha_{1}} + \frac{1}{\alpha_{2}} + \ldots + \frac{1}{\alpha_{i}} + \ldots + \frac{1}{\alpha_{n}}} )}$

The probability coefficient α mentioned above influences the value ofthe probability. The constant k may be used to fine tune the formula,since, by varying its value, the respective weight accorded to roadclass and angle can be varied. Of course, the probability could be basedupon angle without road class if desired.

In these embodiments the probability function is based on the assumptionthat the continuation of the incoming path (unless a pre-calculatedroute exists) will be the straightest path or most similar path in termsof class to the currently travelled path.

An example of the results of applying the algorithm to a junction withfour outgoing paths, where no route has been calculated, is shown inFIG. 3A. The incoming path is shown with an arrow pointing toward thejunction. Here the probabilities based on angle and road class accordingto the above formula resulted in path 2 (p2) being determined as themost probable outgoing path. The remaining paths p1, p3 and p4 formalternative outgoing paths with the stated probabilities. The angles inFIG. 3A are with respect to the continuation of the line of the incomingpath shown in dotted lines.

FIG. 3B shows the corresponding results where there is a pre-calculatedroute, such that the follow up of the incoming path is known to be path4 (p4) outgoing from the junction. This shows the way in which theprobabilities associated with the outgoing paths will be adjusted.

While they have been described by reference to an intersection in theform of a junction, the methods of the invention may be applied to othertypes of decision point, such as roundabouts or even plural junctions.In a roundabout it has been found that the loop defining the path aroundthe roundabout may be disregarded, and the roundabout may be treated asa single intersection having outgoing paths corresponding to each (nonrestricted) exit, including an outgoing path corresponding to theopposite carriageway of the incoming path, i.e. representing a full turnaround the roundabout, with a sum of probabilities being 1. The way inwhich the roundabout may be considered is illustrated in FIG. 4A.

FIG. 4B illustrates a way in which the methods may be applied to aplural junction. Here it may be seen that the two proximate junctionsmay be approximated as a single junction for the purposes of determiningprobabilities. All non restricted outgoing paths leaving the twojunctions are considered to leave the single junction approximating theplural junction, and the sum of their probabilities and is taken as 1.

In addition to the above embodiments in which the probabilities ofoutgoing paths are determined based on the angle of the path and theroad class of the path, various other factors may alternatively oradditionally be taken into account when determining a probability foreach outgoing path. These may be taken into account by suitableadaptation of the probability function in equation 1 to introducefurther terms, which may be weighted as desired as known in the art.

For example, the probability of a given outgoing path may additionallybe based on whether a manoeuvre from an incoming path to an outgoingpath is weighted either more positively or negatively that typicallyexpected in the digital map data. For example, a complicated manoeuvreat a junction may also be a common manoeuvre, and is marked as a specialcase in the digital map data for the junction. Conversely, a seeminglysimple manoeuvre may in reality be dangerous or simply not often used,and is also marked appropriately in the digital map data for thejunction.

The probability of a given outgoing path may additionally be based on anaverage speed associated with the road segment defining the path asindicated by speed profile data associated with the segment. The speedprofile is indicative of an average speed of travel along the segment.As known in the art, digital map data may include speed profile dataassociated with each road segment, based on historical speeds ofvehicles traversing the segment. Such data may be based on vehicle probedata, i.e. data indicative of the position of vehicles with respect totime, e.g. time stamped position data. The speed profile data may be inrespect of a given time period. In some embodiments the probability thata given outgoing path is taken may additionally or alternatively bebased upon the average speed associated with the segment as indicated bythe speed profile data, such that a higher probability will be assignedto a road segment associated with a higher average speed. The averagespeed associated with a segment may be indirectly indicative of its roadclass. Thus the average speed may be used as an alternative to the roadclass in the probability determination above.

In other embodiments the method may, alternatively or additionally,comprise comparing the average speed associated with the road segmentdefining an outgoing path as indicated by the speed profile data to thecurrent speed of travel of the vehicle along the incoming path as itapproaches the junction. A relatively higher probability may be assignedto an outgoing path having an average speed which is closer to thecurrent speed of the vehicle. In other words it may be assumed that thevehicle will continue along a path which requires the smallest change inspeed.

In other embodiments the probability may, alternatively or additionally,be based on a turn history database that is built up for an individualdriver in respect of different junctions of the road network. Each timethat the driver passes through a given junction in the road network, theADAS of the vehicle (or any other suitable electronic device, such as anavigation device) may store data indicative of the incoming andoutgoing path taken, and add this to a database. In this way, for eachjunction, data may be collected representing a count of the number oftimes each type of turn has been taken by the driver at a givenjunction. The turn will represent the type of turn relative to theincoming path, e.g. that path 4 is taken when incoming path is path 1,and may be based on data relating to the incoming and outgoing pathstaken by the driver. This may be used to determine a historicalprobability that the driver has taken a given type of turn at a givenjunction. When the driver approaches the junction this data may be usedin assigning a probability to each of the possible outgoing paths basedon the probability that the path was chosen as an outgoing path based onthe current incoming path previously by the driver. The turn historydatabase may comprise a quantitative probability factor for each type ofturn at the junction, or a relative rank of each type of turn beingtaken.

As will be appreciated, whilst such a turn history database may be builtfor a particular driver (potentially regardless of vehicle), in otherembodiments a turn history database can be built in a similar manner foran individual vehicle, regardless of the person driving the vehicle.

A similar approach may, alternatively or additionally, be used based onvehicle probe data (collected over a relatively long period of time,e.g. weeks, months, etc), i.e. positional data with respect to time, notspecific to the individual driver. The historical probe data may be usedin a similar manner to build up a probability matrix in respect of pathsbeing taken at each of a plurality of junctions in the road network.Probe data relating to the movement of vehicles in the network may befiltered to extract probe traces passing through each junction. Eachtrace may be assigned to a bin depending upon the incoming and outgoingpaths used. Thus there may be a bin for each combination of an outgoingand incoming path at a junction. The data may then be used to obtain acount for each path through the junction, e.g. from a given incomingpath to a given outgoing path. A probability may be determined inrespect of each outgoing path being taken for a given incoming path.When the vehicle approaches a given junction, the relevant data may beobtained from the database representing the probability that eachoutgoing path may be taken based on the current incoming path. In thisway, these probabilities for each outgoing path based on historicalprobe data may be used in determining the probability associated witheach outgoing path, alone, or in combination with other factors asoutlined above.

In accordance with the embodiments of the invention that will bedescribed, probabilities associated with a most probable path andmultiple alternative outgoing paths emanating from the junction aredetermined by the horizon generating subsystem. The horizon generatingsubsystem stores data indicative of each path and its probability.

The horizon generating subsystem may then provide data indicative ofeach path and its associated probability over a vehicle bus to the oneor more subsystems. There are various manners in which this may be done.

It is desirable to reduce the amount of horizon data transmitted overthe CAN bus. For this reason, in certain embodiments, only attributedata for the most probable path is transmitted over the vehicle bus,together with data identifying the location of any such attributes, e.g.relative to the current position of the vehicle. The most probable pathmay be referred to as the “main path”. This is the most probable futuretrajectory of the vehicle up to the limit of the ADAS horizon, asdetermined by the ADAS horizon providing subsystem 3.

At each decision point along the main path there will be a possiblealternative path that the vehicle may take if it diverges from the mainpath. An alternative path that emanates from a decision point along themain path may be referred to as a first level sub path beneath the mainpath. A path branching off from the first level sub path is referred toas a second level sub path and so on. This concept is illustrated byreference to FIGS. 5A, 5B and 5C.

FIG. 5A illustrates a portion of a road network ahead of a currentposition 20 of a vehicle up to a distance in the direction of traveldefined by a limit of the distance that the ADAS horizon will extendonce generated, e.g. 200 m. The road network is made up of a pluralityof links or road segments, e.g. 21, 22, connected by nodes e.g. 24. Thegeneration of the ADAS horizon considers possible paths, i.e.trajectories, that may be taken by the vehicle through the road networkrather than individual road segments and nodes.

FIG. 5B illustrates a number of paths which may be taken through thenetwork shown in FIG. 5A. Each of the paths has a probability that thedriver will follow it. This may be used to determine the most probableor main path that can be expected to be followed, and in many cases atleast a first level sub path. The first level sub path may be consideredto be an alternative path that may be taken at a given decision pointalong the main path.

FIG. 5C illustrates the way in which these paths may be represented toan ADAS application. This represents schematically the relationshipbetween the possible paths through the road network. Path 2 forms themost probable or main path in this case, and paths 1, 3 and 4 are firstlevel sub paths diverging from the main path at different respectivedecision points along its length. Path 5 is a second level sub pathsdiverging from the first level sub paths 4 at a decision point along itslength.

The ADAS horizon generating subsystem 3 will determine the mostprobable, i.e. main path 2. As discussed above, in some simple systems,the ADAS horizon generating subsystem could just transmit attribute datafor this main path over the vehicle bus. An example of such atransmitted horizon is shown in FIG. 6A. However, if the vehiclediverges from the main path, then the system will be left “blind” untila new most probable or main path is generated. Thus, it is beneficialfor the horizon generating subsystem 3 to also determine at least thefirst order sub paths diverging from the main path.

Where one or more first level sub paths are determined, the horizongenerating subsystem 3 may provide attribute data for the or each firstlevel sub path over the vehicle bus to the ADAS applications, togetherwith the corresponding data for the main or most probable path. However,to reduce the amount of data transmitted, in some arrangements onlyminimal data is transmitted regarding the presence of a first level subpath and its location along the main path. This may be done by providinga suitable stub marking a position along the main path at which a firstlevel sub path is present. The stub position may be defined by referenceto an offset from the start of the currently traversed road segmentdefining the main path. FIG. 6B illustrates the form of a possiblehorizon to be transmitted in this case. If the ADAS applications requireadditional data regarding the course and properties of a first level subpath, e.g. if the vehicle diverges from the main path, then the stub maybe used to request the attribute data the first level sub path from theADAS horizon provider, which may then be transmitted over the vehiclebus to the ADAS applications. Again, the ADAS applications would be lefttemporarily blind in this situation.

Another option is shown in FIG. 6C. Here attribute data is transmittedrelating to the each of the first level sub paths as well as relating tothe main path. This may enable the ADAS applications to continue tooperate even if the vehicle starts to travel along one of the firstlevel sub paths rather than the main path. Any second level sub pathsmay be transmitted as stubs as with the first level sub paths in theFIG. 6B arrangement. In preferred embodiments of the inventioninformation about the first and second level sub paths is determined andtransmitted over the vehicle bus.

When a most probable and one or more alternative path at a decisionpoint is determined in accordance with the invention, the horizonprovider may represent the determined paths in any of these manners tothe ADAS applications. Each alternative outgoing path at the decisionpoint, e.g. junction may be represented as a first level sub pathemanating from the main or most probable path at the junction.

In preferred embodiments the horizon provider provides attribute datafor the main or most probable path at the junction, together with stubdata indicative of the position of each alternative outgoing pathassociated with the junction along the main path over the vehicle bus.The stub data may include data indicative of each alternative outgoingpath that exists at the junction and its probability where multiplepaths exist. This data is included in horizon data transmitted over thevehicle bus to the ADAS applications. The probability data ensures thatthe new path may be more readily identified if the vehicle diverges fromthe main path. As in preferred embodiments only stub data indicative ofthe presence of each alternative path and its probability istransmitted, the amount of data needing to be transmitted over thevehicle bus is reduced.

The data transmitted regarding the main path may include any of thefollowing data about attributes of the road segment or segments makingup the determined portion of the main path: speed limit, recommendedspeed limit where no legal speed limit is associated with the roadsegment, functional road class, form of way, gradient, curvature, etc.

The data may be used by the ADAS applications as desired. In preferredembodiments the received horizon data is used to carry out at least oneof; providing an overspeed warning, adjusting a current speed, oroperating a braking subsystem of the vehicle. The ADAS applications maycontrol speed based on a curvature, gradient or speed limit associatedwith the most probable or main path.

Although the present invention has been described with reference topreferred embodiments, it will be understood by those skilled in the artthat various changes in form and detail may be made without departingfrom the scope of the invention as set forth in the accompanying claims.

1-25. (canceled)
 26. A method of generating a horizon for use in anAdvanced Driver Assistance System (ADAS) of a vehicle using storeddigital map data, wherein the digital map data comprises a plurality ofsegments representative of roads of a road network, said methodcomprising: determining a segment representing a road on which thevehicle is currently travelling based on an identified current locationof the vehicle; using the determined segment to identify an upcomingdecision point of the road network from the digital map data;determining an incoming path to the decision point with respect to whichoutgoing paths are to be defined; identifying if the decision point is aroundabout from the digital map data, and, when the decision point isdetermined to be a roundabout, treating the roundabout as a singlejunction such that the outgoing paths of the decision point correspondto exits of the roundabout; determining data indicative of a relativeprobability that each of a plurality of possible outgoing pathsassociated with the decision point will be taken by the vehicle usingone or more of stored digital location-based data, vehicle data anddriver data; determining one or more predicted paths that the vehiclewill be expected to travel in the immediate future at the decision pointusing the data indicative of a relative probability; and generating thehorizon using the one or more predicted paths.
 27. The method of claim26, wherein each segment of the digital map data is associated with dataindicative of one or more attributes of the road represented by thesegment, and wherein the digital location-based data used to determinethe data indicative of a relative probability comprises the attributedata.
 28. The method of claim 27, wherein the attribute data includesdata indicative of: a geometry of the road; a gradient of the road; anangle of the road; a road class of the road; a speed limit associatedwith the road; vehicle flow data indicative of vehicle flow along theroad; and vehicle speed profile data for the road.
 29. The method ofclaim 26, wherein the vehicle data is data indicative of one or more of:vehicle type, vehicle speed, and historical movements of the vehicle,optionally a turn history of the vehicle.
 30. The method of claim 26,further comprising using data indicative of a historical relativeprobability that each of the plurality of possible outgoing paths fromthe decision point has been taken in respect of the incoming path todetermine the data indicative of the relative probability that each ofthe plurality of outgoing paths at a decision point will be taken by thevehicle.
 31. The method of claim 26, wherein the data indicative of therelative probability that each of the possible outgoing paths will betaken is determined based on data indicative of historical paths takenby the individual driver and/or vehicle at the decision point.
 32. Themethod of claim 26, further comprising ranking the plurality of possibleoutgoing paths according to the likelihood that the vehicle may beexpected to travel along the paths and/or determining a probabilityfactor in respect of each path indicative of the relative probabilitythat the path will be taken.
 33. The method of claim 26, whereingenerating the horizon comprises predicting a most probable outgoingpath and at least one alternative outgoing path that the vehicle may beexpected to travel in the immediate future at a decision point, whereinthe stored digital location-based data, vehicle data and/or driver datais used in determining the most probable path and/or the at least onealternative path.
 34. The method of claim 26, wherein generating thehorizon is carried out by a horizon generating subsystem of an ADASassociated with a vehicle, the method further comprising the horizongenerating subsystem providing data associated with the generatedhorizon over a vehicle bus to one or more ADAS applications of thevehicle for use by the one or more applications in controlling one ormore vehicle subsystems.
 35. A method of generating a horizon for use inan Advanced Driver Assistance System (ADAS) of a vehicle using storeddigital map data, wherein the digital map data comprises a plurality ofsegments representative of roads of a road network, said methodcomprising: determining a segment representing a road on which thevehicle is currently travelling based on an identified current locationof the vehicle; using the segment to identify an upcoming decision pointof the road network from the digital map data; determining an incomingpath to the decision point with respect to which outgoing paths are tobe defined; identifying if the decision point is a plural junction fromthe digital map data, and, when the decision point is determined to be aplural junction, treating the plural junction as a single junction suchthat the outgoing paths of the decision point correspond to outgoingpaths of the plurality of proximate junctions forming the pluraljunction; determining data indicative of a relative probability thateach of a plurality of possible outgoing paths associated with thedecision point will be taken by the vehicle using one or more of storeddigital location-based data, vehicle data and driver data; determiningone or more predicted paths that the vehicle will be expected to travelin the immediate future at the decision point using the data indicativeof a relative probability; and generating the horizon using the one ormore predicted paths.
 36. The method of claim 35, wherein each segmentof the digital map data is associated with data indicative of one ormore attributes of the road represented by the segment, and wherein thedigital location-based data used to determine the data indicative of arelative probability comprises the attribute data.
 37. The method ofclaim 36, wherein the attribute data includes data indicative of: ageometry of the road; a gradient of the road; an angle of the road; aroad class of the road; a speed limit associated with the road; vehicleflow data indicative of vehicle flow along the road; and vehicle speedprofile data for the road.
 38. The method of claim 35, wherein thevehicle data is data indicative of one or more of: vehicle type, vehiclespeed, and historical movements of the vehicle, optionally a turnhistory of the vehicle.
 39. The method of claim 35, further comprisingusing data indicative of a historical relative probability that each ofthe plurality of possible outgoing paths from the decision point hasbeen taken in respect of the incoming path to determine the dataindicative of the relative probability that each of the plurality ofoutgoing paths at a decision point will be taken by the vehicle.
 40. Themethod of claim 35, wherein the data indicative of the relativeprobability that each of the possible outgoing paths will be taken isdetermined based on data indicative of historical paths taken by theindividual driver and/or vehicle at the decision point.
 41. The methodof claim 35, further comprising ranking the plurality of possibleoutgoing paths according to the likelihood that the vehicle may beexpected to travel along the paths and/or determining a probabilityfactor in respect of each path indicative of the relative probabilitythat the path will be taken.
 42. The method of claim 35, whereingenerating the horizon comprises predicting a most probable outgoingpath and at least one alternative outgoing path that the vehicle may beexpected to travel in the immediate future at a decision point, whereinthe stored digital location-based data, vehicle data and/or driver datais used in determining the most probable path and/or the at least onealternative path.
 43. The method of claim 35, wherein generating thehorizon is carried out by a horizon generating subsystem of an ADASassociated with a vehicle, the method further comprising the horizongenerating subsystem providing data associated with the generatedhorizon over a vehicle bus to one or more ADAS applications of thevehicle for use by the one or more applications in controlling one ormore vehicle subsystems.
 44. A non-transitory computer readable mediumstoring instructions that, when executed by a processor, cause theprocessor to perform a method for generating a horizon for use in anAdvanced Driver Assistance System (ADAS) of a vehicle using storeddigital map data, wherein the digital map data comprises a plurality ofsegments representative of roads of a road network, said methodcomprising: determining a segment representing a road on which thevehicle is currently travelling based on an identified current locationof the vehicle; using the segment to identify an upcoming decision pointof the road network from the digital map data; determining an incomingpath to the decision point with respect to which outgoing paths are tobe defined; identifying if the decision point is a roundabout from thedigital map data, and, when the decision point is determined to be aroundabout, treating the roundabout as a single junction such that theoutgoing paths of the decision point correspond to exits of theroundabout; determining data indicative of a relative probability thateach of a plurality of possible outgoing paths associated with thedecision point will be taken by the vehicle using one or more of storeddigital location-based data, vehicle data and driver data; determiningone or more predicted paths that the vehicle will be expected to travelin the immediate future at the decision point using the data indicativeof a relative probability; and generating the horizon using the one ormore predicted paths.
 45. A non-transitory computer readable mediumstoring instructions that, when executed by a processor, cause theprocessor to perform a method for generating a horizon for use in anAdvanced Driver Assistance System (ADAS) of a vehicle using storeddigital map data, wherein the digital map data comprises a plurality ofsegments representative of roads of a road network, said methodcomprising: determining a segment representing a road on which thevehicle is currently travelling based on an identified current locationof the vehicle; using the segment to identify an upcoming decision pointof the road network from the digital map data; determining an incomingpath to the decision point with respect to which outgoing paths are tobe defined; identifying if the decision point is a plural junction fromthe digital map data, and, when the decision point is determined to be aplural junction, treating the plural junction as a single junction suchthat the outgoing paths of the decision point correspond to outgoingpaths of the plurality of proximate junctions forming the pluraljunction; determining data indicative of a relative probability thateach of a plurality of possible outgoing paths associated with thedecision point will be taken by the vehicle using one or more of storeddigital location-based data, vehicle data and driver data; determiningone or more predicted paths that the vehicle will be expected to travelin the immediate future at the decision point using the data indicativeof a relative probability; and generating the horizon using the one ormore predicted paths.
 46. A system for generating a horizon for use inan Advanced Driver Assistance System (ADAS) of a vehicle using storeddigital map data, wherein the digital map data comprises a plurality ofsegments representative of roads of a road network, said systemcomprising: means for determining a segment representing a road on whichthe vehicle is currently travelling based on an identified currentlocation of the vehicle; means for using the segment to identify anupcoming decision point of the road network from the digital map data;means for determining an incoming path to the decision point withrespect to which outgoing paths are to be defined; means for identifyingif the decision point is a roundabout from the digital map data, and,when the decision point is determined to be a roundabout, treating theroundabout as a single junction such that the outgoing paths of thedecision point correspond to exits of the roundabout; means fordetermining data indicative of the relative probability that each of aplurality of possible outgoing paths associated with the decision pointwill be taken by the vehicle using one or more of stored digitallocation-based data, vehicle data and driver data; means for determiningone or more predicted paths that the vehicle will be expected to travelin the immediate future at the decision point using the data indicativeof a relative probability; and means for generating the horizon usingthe one or more predicted paths.
 47. The system of claim 46, wherein thesystem is configured to provide data associated with the generatedhorizon over a vehicle bus to one or more ADAS applications of thevehicle for use by the one or more applications in controlling one ormore vehicle subsystems.
 48. A system for generating a horizon for usein an Advanced Driver Assistance System (ADAS) of a vehicle using storeddigital map data, wherein the digital map data comprises a plurality ofsegments representative of roads of a road network, said systemcomprising: means for determining a segment representing a road on whichthe vehicle is currently travelling based on an identified currentlocation of the vehicle; means for using the segment to identify anupcoming decision point of the road network from the digital map data;means for determining an incoming path to the decision point withrespect to which outgoing paths are to be defined; means for identifyingif the decision point is a plural junction from the digital map data,and, when the decision point is determined to be a plural junction,treating the plural junction as a single junction such that the outgoingpaths of the decision point correspond to outgoing paths of theplurality of proximate junctions forming the plural junction; means fordetermining data indicative of the relative probability that each of aplurality of possible outgoing paths associated with the decision pointwill be taken by the vehicle using one or more of stored digitallocation-based data, vehicle data and driver data; means for determiningone or more predicted paths that the vehicle will be expected to travelin the immediate future at the decision point using the data indicativeof a relative probability; and means for generating the horizon usingthe one or more predicted paths.
 49. The system of claim 48, wherein thesystem is configured to provide data associated with the generatedhorizon over a vehicle bus to one or more ADAS applications of thevehicle for use by the one or more applications in controlling one ormore vehicle subsystems.